Skip Headers

Oracle® OLAP DML Reference 10g Release 2 (10.2) Part Number B14346-01 |
Home | Book List | Contents | Index | Master Index | Feedback

Previous | Next
| View PDF

# COMPILEWARN

The COMPILEWARN option controls whether Oracle OLAP records a warning message in the current outfile when a compilable object, such as a program or a model, is being compiled automatically. (When you use the COMPILE command to explicitly compile an object, Oracle OLAP does not display the COMPILEWARN message.)

A compilable object is automatically compiled in the following cases:

- The first time it is executed after being edited.

- The first time it is executed in a session when it was compiled in a previous session after the last time the analytic workspace was updated and committed.

- After an analytic workspace object referred to in the code has been renamed or deleted. When the object name in the code has not been redefined, you will receive an error message.

- When the code refers to objects in another analytic workspace and the objects in the currently attached analytic workspace do not have the same object type (variable, relation, and so on), data type (`INTEGER`, `TEXT`, and so on), or dimensions as the objects available when the code was previously compiled.

Data type

BOOLEAN

Syntax

COMPILEWARN = {YES|NO}

Arguments

YES

  Oracle OLAP records a message warning you that a compilable object is being compiled automatically. The message explains why the compilation was necessary.

NO

  (Default) Oracle OLAP does not record a message warning you that an object is being compiled automatically.

Examples

Example 9-16 Specifying That You Want Compiler Warnings

When COMPILEWARN is set to `YES`, when you run the `do_report` program just after editing it, Oracle OLAP places the following message in your current outfile before the `do_report` output.

    DO_REPORT is being automatically compiled.